System for creating video file for audio snippet of podcast audio file and related methods

ABSTRACT

An audio podcast distribution system includes a server configured to aggregate and store podcast audio files in a database. A computing device is configured to render an audio playback GUI on a display for playing a given podcast audio file from the database. The audio playback GUI includes a playback control user input, and an audio snippet creation user input. The computing device is configured to render an audio snippet playback GUI on the display, the audio snippet playback GUI include a video creation user input, and when the video creation user input is activated, send a video request to the server. The server is configured to, based upon the video request, generate a video file having the audio snippet of the given podcast audio file, and image data in the database associated with the given podcast audio file.

RELATED APPLICATION

This application is a continuation-in-part of prior filed copendingapplication Ser. No. 17/661,358 filed Apr. 29, 2022, the entire subjectmatter of which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The present disclosure relates to the field of audio processing system,and, more particularly, to an audio podcast distribution system andrelated methods.

BACKGROUND

A podcast is a program made available in digital format (typically audioformat) for download over the Internet. Although not required for theformat, most podcasts are episodic in nature, for example, delivereddaily or weekly. The popularity of podcasts has increased substantiallyover the last decade even though the format is nearly twenty years old.Indeed, the format arguably languished for the first few years of itsexistence. For example, in 2006, podcast awareness was a mere 22% of theUnited States population, and that figure has risen to 78% in the nextsixteen years.

One of the main drivers of the popularity of the format was theimprovement in the applications for listening to podcasts. In the earlyyears, podcast applications were application specific and did verylittle else. As the format became more mature, several large players inthe mobile software field integrated podcast functionality into theiraudio players, which increased access to the format. More importantly,ecosystems within those audio players developed and permitted ratingsand rankings of podcasts.

Once drawback to podcast applications is the inability for users toshare the podcasts. Most applications permit you to share the podcastfeed so others may subscribe to the same format. Some applications mayeven permit you to share the entire podcast in a compressed format, suchas MP3. Nonetheless, for long form podcasts, which can last severalhours, this is a bit cumbersome and inconvenient for the user.

SUMMARY

Generally, an audio podcast distribution system comprises a serverconfigured to aggregate and store a plurality of podcast audio files ina database, and at least one computing device in communication with theserver. The at least one computing device comprises a processor and adisplay coupled to the processor. The processor is configured to renderan audio playback graphical user interface (GUI) on the display forplaying a given podcast audio file from the database. The audio playbackGUI comprises a playback control user input, and an audio snippetcreation user input. The processor is configured to when the audiosnippet creation user input is activated, render an audio snippetcreation GUI for generating an audio snippet of the given podcast audiofile, and upload at least one file parameter for the audio snippet ofthe given podcast audio file to the database. The processor is alsoconfigured to render an audio snippet playback GUI on the display, theaudio snippet playback GUI comprising a video creation user input, andwhen the video creation user input is activated, send a video request tothe server, the video request being associated with the audio snippet ofthe given podcast audio file. The server is configured to, based uponthe video request, generate a video file comprising the audio snippet ofthe given podcast audio file, and image data in the database associatedwith the given podcast audio file.

Additionally, the server may be configured to add the video file of theaudio snippet of the given podcast audio file to the database, andgenerate a custom link to access the video file within the database. Insome embodiments, the server may be configured to generate the videofile by at least generating sequential screenshots of the audio snippetplayback GUI, and combining the sequential screenshots with the audiosnippet of the given podcast audio file. The server may be configured toaccess the video file when another video request is received for thesame audio snippet of the given podcast audio file.

Also, the audio snippet creation GUI may comprise a visual waveforminput, and an audio snippet creation playback control user input. Theserver may be configured to add the audio snippet of the given podcastaudio file to the database, and generate a custom link to access theaudio snippet within the database.

In some embodiments, the at least one computing device may comprise aplurality of computing devices configured to respectively upload aplurality of audio snippets to the server, and the server may beconfigured to rank the plurality of audio snippets based upon heuristicsdata for respective users associated with the plurality of computingdevices. The heuristic data may comprise audio playback data and audioplayback completion event data. The processor may be configured torender an audio snippet discovery GUI on the display for viewing theplurality of audio snippets, the audio snippet discovery GUI configuredto receive swipe input to scroll through the plurality of audiosnippets.

Another aspect is directed to a method for operating an audio podcastdistribution system comprising at least one computing device, and aserver configured to aggregate and store a plurality of podcast audiofiles in a database. The at least one computing device is incommunication with the server. The method comprises rendering an audioplayback GUI on a display of the at least one computing device forplaying a given podcast audio file from the database. The audio playbackGUI comprises a playback control user input, and an audio snippetcreation user input. The method also includes when the audio snippetcreation user input is activated, rendering an audio snippet creationGUI on the display of the at least one computing device for generatingan audio snippet of the given podcast audio file, and uploading at leastone file parameter for the audio snippet of the given podcast audio fileto the database. The method also includes rendering an audio snippetplayback GUI on the display of the at least one computing device, theaudio snippet playback GUI comprising a video creation user input, andwhen the video creation user input is activated, send a video request tothe server. The video request is associated with the audio snippet ofthe given podcast audio file. The method also includes generating, atthe server, based upon the video request a video file comprising theaudio snippet of the given podcast audio file, and image data in thedatabase associated with the given podcast audio file.

Yet another aspect is directed to a non-transitory computer-readablemedium for operating an audio podcast distribution system comprising atleast one computing device, and a server configured to aggregate andstore a plurality of podcast audio files in a database. The at least onecomputing device is in communication with the server. The non-transitorycomputer-readable medium has computer-executable instructions forcausing the at least one computing device and the server to performsteps comprising rendering an audio playback GUI on a display of the atleast one computing device for playing a given podcast audio file fromthe database. The audio playback GUI comprises a playback control userinput, and an audio snippet creation user input. The steps also includeswhen the audio snippet creation user input is activated, rendering anaudio snippet creation GUI on the display of the at least one computingdevice for generating an audio snippet of the given podcast audio file,and uploading at least one file parameter for the audio snippet of thegiven podcast audio file to the database. The steps also includesrendering an audio snippet playback GUI on the display of the at leastone computing device, the audio snippet playback GUI comprising a videocreation user input, and when the video creation user input isactivated, send a video request to the server. The video request isassociated with the audio snippet of the given podcast audio file. Thesteps also includes generating, at the server, based upon the videorequest a video file comprising the audio snippet of the given podcastaudio file, and image data in the database associated with the givenpodcast audio file.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a first embodiment of an audio podcastdistribution system, according to the present disclosure.

FIGS. 2-16 are screenshots of an example embodiment GUI from thecomputing device of the audio podcast distribution system of FIG. 1 .

FIG. 17 is a schematic diagram of a second embodiment of the audiopodcast distribution system, according to the present disclosure.

FIGS. 18-22 are screenshots of an example embodiment GUI from thecomputing device of the audio podcast distribution system of FIG. 17 .

FIG. 23 is a schematic diagram of a third embodiment of the audiopodcast distribution system, according to the present disclosure.

DETAILED DESCRIPTION

The present disclosure will now be described more fully hereinafter withreference to the accompanying drawings, in which several embodiments ofthe invention are shown. This present disclosure may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein. Rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the present disclosure to those skilled in theart. Like numbers refer to like elements throughout.

Referring initially to FIG. 1 , an audio podcast distribution system 100according to the present disclosure is now described. The audio podcastdistribution system 100 illustratively includes a server 101 configuredto aggregate and store a plurality of podcast audio files 102 in adatabase 103, and a plurality of computing devices 104 a-104 n incommunication with the server over the Internet 105. The server 101 isconfigured to check for new podcast audio files 102 periodically, forexample, every 15 minutes. As will be appreciated, the server 101 mayuse Really Simple Syndication (RSS) feeds to monitor for new files.

The server 101 may comprise one or more of assigned resources on a cloudcomputing platform (e.g. Google Cloud Platform, Amazon Web Services, andMicrosoft Azure) and a stand-alone computing device. For illustrativeclarity, only one of the plurality of computing devices 104 a is shownin detail, but it should be appreciated that the other computing devicesmay be similarly constituted. Also, the plurality of computing devices104 a-104 n may comprise one or more of the following computing devicetypes: a mobile device type, a mobile cellular device type, a tabletcomputing device type, a desktop computing device type, or a laptopcomputing device type.

The computing device 104 a illustratively comprises a processor 106 anda display 107 coupled to the processor. In some embodiments, the display107 may comprise a touchscreen input display. In other embodiments, thecomputing device 104 a may include other input/output devices, such as amouse device or keyboard device.

The processor 106 is configured to execute podcast software foraccessing the server 101 and the plurality of podcast audio files 102 inthe database 103. As will be appreciated, the podcast software may beimplemented via a native operating system of the computing device 104 a,and/or be implemented within a web browser, for example, using Web 3.0features. As will be appreciated, the podcast software includes a GUIwith multiple subpart GUIs.

Referring now additionally to FIGS. 2-16 , the processor 106 isconfigured to render an audio playback GUI 110 on the display 107 forplaying a given podcast audio file 102 from the database 103. The audioplayback GUI 110 includes a playback control user input 111 (i.e. theplay/pause button, the rewind 15 seconds button, and the forward 15seconds button), and an audio snippet creation user input 112. Theprocessor is configured to when the audio snippet creation user input112 is activated, render an audio snippet creation GUI 113 (FIGS. 12-15) for generating an audio snippet 114 of the given podcast audio file102, and upload the audio snippet of the given podcast audio file to thedatabase 103. Of course, in other embodiments, the server 101 may createthe audio snippet 114.

In the illustrated embodiment, some or all of the plurality of computingdevices 104 a-104 n are configured to respectively upload a plurality ofaudio snippets 114 to the server 101. The server 101 is configured torank the plurality of audio snippets 114 and the plurality of podcastaudio files 102 based upon heuristics data for respective users 115a-115 n associated with the plurality of computing devices 104 a-104 b.The heuristic data may comprise audio playback data and audio playbackcompletion event data. In some embodiments, the server 101 is configuredto push a ranked list of the plurality of audio snippets 114 to therespective users 115 a-115 n of the plurality of computing devices 104a-104 n.

The server 101 is configured to add the audio snippet 114 of the givenpodcast audio file 102 to the database 103, and generate a custom linkto access the audio snippet within the database. The server 101 may beconfigured to process the received audio snippet 114 into a compressedaudio format, for example, an MP3 file format. In some embodiments, thecustom link to access the audio snippet 114 within the database 103comprises a uniform resource locator (URL) link for accessing the audiosnippet from the Internet 105. The custom link to access the audiosnippet 114 within the database 103 is parsed by social media crawlersto extract metadata, which permits sharing on the respective socialmedia platforms.

Moreover, the server 101 is configured to monitor access to the customlink to generate additional heuristics data. Also, the podcast softwaretracks the listening behavior of the respective user 115 a-115 n forreporting to the server 101. The podcast software will track audioplays, pauses, scrubbing along the progress bar, and audio playbackcompletion events. Each event is time stamped and includes the playbackposition within the audio. This allows the server 101 to determine thetime spent listening to the given podcast audio file 102.

In some embodiments, the server 101 is configured to process theplurality of podcast audio files 102 to generate suggested audiosnippets for the respective users 115 a-115 n. In particular, the server101 is configured to generate the suggested audio snippets based uponthe heuristics data. In some embodiments, the server 101 is configuredto generate the suggested audio snippets based upon a machine learningmodel. In particular, in a supervised machine learning model, the inputsof the supervised machine learning model would be the waveforms of theplurality of podcast audio files 102, metrics from the waveformsindicative of arguments (i.e. high absolute signal levels), and theheuristics data. The output of the supervised machine learning modelwould be the suggested audio snippets. The supervised machine learningmodel may be a trained using the created audio snippets in therespective users 115 a-115 n as training data.

Also, the server 101 is configured to rank subscribed RSS feeds with apriority factor metric. The priority factor metric may be based uponheuristics data noted herein and serves as a proxy for the popularity ofthe associated podcast audio files 102. The server 101 is configured topoll higher priority factor metric sources first, and then sequentiallylower thereafter. For example, the server 101 is configured to poll 0.8metric value or greater first, then 0.6 metric value or greater, andthen 0.4 metric value or greater first.

In some embodiments, the server 101 is configured to use persistentunique identifiers of the respective user 115 a-115 n to aggregateadvertising data, such as web browsing history, search history, andsocial media interaction history. For example, if the respective user115 a-115 n has been browsing jogging websites and searching for joggingshoes, the server 101 is configured to recommend suggested audiosnippets for the respective user associated with the topic of jogging.Indeed, this advertising data may be included as an input in the machinelearning embodiments.

In some embodiments, the server 101 is configured to render an analyticsGUI for displaying the heuristics data, and other user statistics. Theanalytics GUI may include a user version for the respective users 115a-115 n, and a creator version for podcast authors to monitor thepopularity of their podcast audio files 102. In the creator version UI,the authors may designate multiple categories and subcategories fortheir content files. Also, the server 101 is configured to render acontent management system (CMS) creation tool/GUI for trending topicsnow.

In the illustrated embodiment, the server 101 is configured to store theplurality of podcast audio files 102, the uploaded audio snippets 114,and associated metadata for these files in the database 103. Theassociated metadata may also include keywords and tags, which can besearched within the podcast software. In other embodiments, the storagemay be partially on the plurality of computing devices 104 a-104 b.

In some embodiments, the podcast software may include a playlist UI forstoring a queue of podcast audio files 102, and audio snippets 114. Theplaylist queue may be curated by the respective user 115 a-115 n,feature podcast authors, and ranked lists of system wide audio snippets.

Referring now to FIGS. 2-5 , in particular, the processor is configuredto render a GUI including a home screen GUI 116 on the display 107. Thehome screen GUI 116 illustratively includes a top suggested podcast menu117. The top suggested podcast menu 117 comprises a suggested podcastaudio file 102 for the respective user 115 a-115 n based upon theheuristic data associated with the respective user. The home screen GUI116 illustratively includes a continued playback menu 120 (i.e.restarting prior podcast audio files 102 that were partially listenedto), and a most recent audio snippet menu 121 for accessing recentlycreated audio snippets by the respective user 115 a-115 n.

The home screen GUI 116 illustratively includes a suggested audiosnippet menu 122 including a set of suggested audio snippets 114 fromthe database 103 for the respective user 115 a-115 n based upon theheuristic data associated with the respective user. The home screen GUI116 illustratively includes a plurality of subject matter specific menus123 a-123 b including categorized audio podcast files.

Referring now to FIGS. 6-8 , in particular, the processor is configuredto render a GUI including a favorites screen GUI 124 on the display 107.The favorites screen GUI 124 illustratively includes tabs 125 a-125 baccessing a listing 126 of audio podcast files that have been noted as“liked” within the podcast software, and a listing 127 of audio snippets114 that have been noted as “liked” within the podcast software. Asshown, there are two liked audio podcast files, and three liked audiosnippets 114. If the respective user 115 a-115 n selects any of theliked audio snippets 114, the GUI transitions to a snippet playback GUI130 shown in FIG. 8 . The snippet playback GUI 130 includes a likebutton 131 for toggling the liked status of the given audio snippet 114,and a share button 132 for sharing the given audio snippet.

Referring now to FIGS. 9-10 , in particular, the processor is configuredto render a GUI including a library screen GUI 133 on the display 107.The library screen GUI 133 illustratively includes tabs 134 a-134 baccessing a listing 135 of audio snippets 114 that have created with thepodcast software, and a listing 136 of audio snippets 114 that have beenshared with the podcast software. As shown, there are two created audiosnippets 114, and no shared audio snippets.

Referring now to FIG. 11 , in particular, the processor is configured torender a GUI including an audio playback GUI 110 on the display 107. Theaudio playback GUI 110 illustratively comprises a playback control userinput 111, an audio snippet creation user input 112, a like button 137for toggling the liked status of the given audio podcast file, and ashare button 140 for sharing the given audio podcast.

Referring now to FIGS. 12-15 , the processor 106 is configured to whenthe audio snippet creation user input 112 is activated, render the GUIto comprise the audio snippet creation GUI 113 for generating an audiosnippet 114 of the given podcast audio file 102. In particular, theaudio snippet creation GUI 113 includes a visual waveform input 141, andan audio snippet creation playback control user input 142. The visualwaveform input 141 includes a displayed audio waveform 143, a slidabletime domain selection input 144 for the audio snippet 114 of the givenpodcast audio file 102, and zoom control inputs 145 a-145 b for viewingspecific portions of the audio waveform.

When the zoom control inputs 145 a-145 b are used to zoom out, thedisplayed audio waveform 143 may comprise a waveform extending for anentirety of the given podcast audio file 102. The slidable time domainselection input 144 for the audio snippet 114 may have a defaultposition based upon a current playback position in the given podcastaudio file 102. For example, the default position may comprise placingthe slidable time domain selection input 144 to cover 10 seconds beforethe current playback position and 50 seconds after the current playbackposition. The slidable time domain selection input 144 may have amaximum time duration, such as 60 second, for example. The slidable timedomain selection input 144 for the audio snippet 114 of the givenpodcast audio file 102 comprises first and second vertical bars 146a-146 b (i.e. the start and end marks for the audio snippet) depictingthe currently selected slidable time domain selection input, and a thirdvertical bar 147 (noted with dashes) showing the current playbackposition of the given audio podcast file.

The audio snippet creation GUI 113 illustratively comprises a save input150 for creating the audio snippet 114. Once the audio snippet 114 hasbeen created, the GUI transitions to the snippet playback GUI 130 shownin FIG. 8 . In some embodiments, the audio snippet creation GUI 113 mayinclude a text editing feature for generating a text caption for theaudio snippet 114 of the given podcast audio file 102, which is uploadedand stored as associated metadata.

Referring now to FIG. 16 , the processor 106 is configured to render anaudio snippet discovery GUI 151 on the display 107 for viewing theplurality of audio snippets. The audio snippet discovery GUI 151configured to receive swipe input 152 to scroll through the plurality ofaudio snippets 114.

Another aspect is directed to a method for operating a computing device104 a in an audio podcast distribution system 100 comprising a server101 configured to aggregate and store a plurality of podcast audio files102 in a database 103. Although depicted separately for drawing clarity,it should be appreciated that the database 103 and the server 101 may beintegrated in some embodiments. The computing device 104 a is incommunication with the server 101. The method includes rendering anaudio playback GUI 110 on a display 107 for playing a given podcastaudio file 102 from the database 103. The audio playback GUI 110comprises a playback control user input 111, and an audio snippetcreation user input 112. The method further includes when the audiosnippet creation user input 112 is activated, rendering an audio snippetcreation GUI 113 for generating an audio snippet 114 of the givenpodcast audio file 102, and uploading the audio snippet of the givenpodcast audio file to the database 103.

Yet another aspect is directed to a non-transitory computer-readablemedium for operating a computing device 104 a in an audio podcastdistribution system comprising a server 101 configured to aggregate andstore a plurality of podcast audio files 102 in a database 103. Thecomputing device 104 a is in communication with the server 101. Thenon-transitory computer-readable medium has computer-executableinstructions for causing the computing device 104 a to perform stepscomprising rendering an audio playback GUI 110 on a display 107 forplaying a given podcast audio file 102 from the database 103. The audioplayback GUI 110 comprises a playback control user input 111, and anaudio snippet creation user input 112. The steps further comprises whenthe audio snippet creation user input 112 is activated, rendering anaudio snippet creation GUI 113 for generating an audio snippet 114 ofthe given podcast audio file 102, and uploading the audio snippet of thegiven podcast audio file to the database 103.

In the following, a discussion of an example embodiment of the audiopodcast distribution system 100 is provided. It should be appreciatedthat any of the features discussed below can be incorporated with thefeatures of the embodiments disclosed hereinabove, and vice versa. Here,the computing device 104 a or the server 101 is configured to perform animport process of the plurality of podcast audio files 102. The importprocess begins with an input file (e.g. a comma-separated values (CSV)file) that itemizes the plurality of podcast audio files 102 that are tobe imported onto the audio podcast distribution system 100. The inputfile is parsed and processed so that each discovered podcast audio file102 has a valid category identification, a hex color (denoting thebackground color shown in the companion podcast application), and an RSSuniform resource locator (URL). Each discovered podcast audio file 102has their RSS feed downloaded and parsed in order to extract metadata(e.g. podcast title, description, etc.). The discovered podcast audiofiles 102 that have valid RSS URLs that can be parsed are added to thepodcasts-to-import table in the database 103. Once the input file isfully processed, the import process pivots to the update phase.

During the update phase, the plurality of podcast audio files 102 aredownloaded and stored for future processing. Podcast audio file detailsare extracted from the RSS feed and recorded in a podcast-episodestable. For each episode that is discovered in the RSS, the computingdevice 104 a will attempt to download the audio file (e.g. MP3 formatfile) associated with the episode. The downloaded episode is stored forepisode playback within the computing device 104 a and in order togenerate audio clips later when the respective user 115 a-115 n createsthe audio snippet. Once downloaded, the podcast audio file is verifiedas a valid audio format file. If the podcast audio file passesverification, the computing device 104 a uses a PHP audio waveformgenerator to extract audio peaks in order to generate the audiovisualization in the podcast software. The waveform generator uses theSoX library to manipulate audio, as available from Source Forge. The SoXlibrary is also used later to generate audio snippets. The episode peaksare stored in the database in order to avoid having to re-generate thedata on demand later. Once a file has audio peaks data associated withit, it becomes available in the podcast software.

In this embodiment, the audio podcast distribution system 100 mayprovide for podcast discovery. In particular, the audio podcastdistribution system 100 leverages a two-prong approach to showcasecontent that will engage the user 115 a-115 n. The first is the homepage layout (i.e. the home screen GUI 116) that aggregates potentiallycompelling content into distinct sections. The banner area (i.e. the topsuggested podcast menu 117) of the homepage shows six random podcaststhat have been flagged as featured in the database 103. The “Jump BackIn” section (i.e. the continued playback menu 120) allows users 115a-115 n to resume playback between podcast software sessions. The “MostRecent Cherries” section (i.e. the most recent audio snippet menu 121)lists the eight of the most recently created audio snippets across allcategories. The “Cherries For You” section (i.e. the suggested audiosnippet menu 122) lists a random selection of the six of the mostrecently created audio snippets across all subscribed categories for therespective user 115 a-115 n. Finally, the homepage shows up to threerandom categories (i.e. the subject matter specific menus 123 a-123 b)that the respective user 115 a-115 n is subscribed to. Each categorysection shows three random audio snippets and three random audio podcastfiles.

The second approach to content discovery is the audio stream feature,which is provided within the audio snippet discovery GUI 151. The audiostream is available as a pull-up component on the podcast software. Theaudio snippet discovery GUI 151 will populate with a random selection ofepisodes and audio snippets based on the subscribed categories of therespective user 115 a-115 n. The audio snippet discovery GUI 151 willtrigger playback of the next piece of content upon completion of thecurrent audio. Alternatively, the respective user 115 a-115 n can scrolldown to skip the current content and continuously discover new podcasts.

In this embodiment, the audio podcast distribution system 100 mayprovide for audio snippet creation. When the respective user 115 a-115 nchooses to create an audio snippet from an episode, the podcast softwaretransitions to the audio snippet creation GUI 113 where the respectiveuser's current playback position is marked on the audio waveformvisualization. A pre-selected sixty second section or region of thewaveform is highlighted. The respective user 115 a-115 n may drag theentire highlighted area back and forth along the waveform, and can alsoadjust the beginning and ending of the clip manually by sliding thefirst and second vertical bars 146 a-146 b. Once the respective user 115a-115 n has finalized their selection, their request is submitted to theserver 101 to generate a new MP3 file using the start time and durationsubmitted (e.g. using the first and SOX library). The newly createdaudio snippet is stored on the server 101 and indexed in the database103 for showcasing within the podcast software.

Advantageously, the audio podcast distribution system 100 may providefor enhanced usability over existing podcast software applications. Inparticular, the audio podcast distribution system 100 provides forsuperior sharing features by allowing the user 115 a-115 n to createsharable audio snippets 114 of the given podcast audio file 102 in bandand within the same software application. Helpfully, the audio snippet114 is conveniently uploaded to the server 101 for easy sharing andaccess. Moreover, the audio podcast distribution system 100 aggregatesand ranks the audio snippets 114 from all the users 115 a-115 n, andprovides for improved content discovery.

Referring now additionally to FIGS. 17-22 , another embodiment of theaudio podcast distribution system 200 is now described. In thisembodiment of the audio podcast distribution system 200, those elementsalready discussed above with respect to FIGS. 1-16 are incremented by100 and most require no further discussion herein. This embodimentdiffers from the previous embodiment in that this audio podcastdistribution system 200 is configured to generate sharable video filesof the audio snippets 214. It should be appreciated by those skilled inthe art that the features of the disclosed audio podcast distributionsystems 100, 200 may be selectively combined.

As shown in FIG. 18 , the processor 206 of the computing device 204 a isconfigured to render an audio snippet playback GUI 260 on the display207 when a given audio snippet 214 is selected for playback. The audiosnippet playback GUI 260 illustratively comprises a submenu input 261,which provides access to an audio snippet submenu 262 shown in FIG. 19 .The audio snippet submenu 262 illustratively includes a video creationuser input 263 a, a favorite user input 263 b for classifying the givenaudio snippet 214 as a favorite for the user 215 a, a playlist userinput 263 c for adding the given audio snippet onto a playlist for theuser 215 c, and a cancel user input 263 d for exiting the audio snippetsubmenu.

The processor 206 is configured to when the video creation user input263 a is activated, send a video request (e.g., communication messagesent over the Internet 205) to the server 201. The video request isassociated with the audio snippet 214 of the given podcast audio file(i.e. the one being played currently within the audio snippet playbackGUI 260: “The BOCL Show”).

The server 201 is configured to, based upon the video request, generatea video file comprising the audio snippet 214 of the given podcast audiofile 202, and image data 265 in the database 203 associated with thegiven podcast audio file. As will be appreciated by those skilled in theart, the image data 265 in the database 203 associated with the givenpodcast audio file 202 may comprise the illustrated example of albumcover image data from the given podcast audio file. In some embodiments,if the given podcast audio file 202 was derived from a full length videopodcast source (i.e., the given podcast audio file was derived from theaudio track of the video podcast source), the image data may comprisethe original video data associated with the audio snippet 214.

Once the server 201 receives the video request, the audio snippetplayback GUI 260 transitions to a processing mode shown in FIG. 20 .Here, the audio snippet playback GUI 260 illustratively comprises aplayback input 266 miniaturized at a bottommost edge of the display 207,and a status indicator 267 for providing a status of the processing ofthe video file.

To avoid duplicative processing and storage, the server 201 isconfigured to access the video file when another video request isreceived for the same audio snippet 214 of the given podcast audio file202. In other words, if another user 215 a-215 n generates a videorequest for the same audio snippet 214 of the given podcast audio file202, rather than creating another video file, the server 201 retrievesthe stored information from the prior created video file and providesthat to the other user.

Once the video file has been processed by the server 201, the audiosnippet playback GUI 260 transitions to a completion stage shown in FIG.21 . Additionally, the server 201 is illustratively configured to addthe video file of the audio snippet 214 of the given podcast audio file202 to the database 203, and generate a custom link to access the videofile within the database. Here, the audio snippet playback GUI 260illustratively comprises a play input 270 a for playing the video filefrom the server 201, a download input 270 b to download the video fileto the computing device (i.e. as shown in the library screen GUI 233 ofFIG. 22 ), and a link field 270 c providing the custom link to accessthe video file within the database 203 for sharing on social mediaplatforms (e.g., YouTube, Instagram Reels, Tiktok, etc.). In someembodiments, the server 201 may be configured to generate the video fileby at least generating sequential screenshots of the audio snippetplayback GUI 260 using a headless web browser instance, for example, andcombining the sequential screenshots with the audio snippet 214 of thegiven podcast audio file 202.

Another aspect is directed to a method for operating an audio podcastdistribution system 200 comprising at least one computing device 204a-204 n, and a server 201 configured to aggregate and store a pluralityof podcast audio files 202 in a database 203. The at least one computingdevice 204 a-204 n is in communication with the server 201. The methodcomprises rendering an audio playback GUI 110 (FIG. 11 ) on a display207 of the at least one computing device 204 a-204 n for playing a givenpodcast audio file 202 from the database 203. The audio playback GUI 110comprises a playback control user input 111 (FIG. 11 ), and an audiosnippet creation user input 112 (FIG. 11 ). The method also includeswhen the audio snippet creation user input 112 is activated, renderingan audio snippet creation GUI 113 (FIG. 12 ) on the display of the atleast one computing device for generating an audio snippet 214 of thegiven podcast audio file 202, and uploading a plurality of fileparameters for the audio snippet of the given podcast audio file to thedatabase 203. The plurality of file parameters may comprise an episodeID, a user ID, a start time, and a time duration, for example. As willbe appreciated, the plurality of file parameters is used by the serverto 201 to create the audio snippet 214.

The method also includes rendering an audio snippet playback GUI 260 onthe display 207 of the at least one computing device 204 a-204 n. Theaudio snippet playback GUI 260 comprises a video creation user input 263a, and when the video creation user input is activated, send a videorequest to the server 201. The video request is associated with theaudio snippet 214 of the given podcast audio file 202. The method alsoincludes generating, at the server 201, based upon the video request avideo file comprising the audio snippet 214 of the given podcast audiofile 202, and image data 265 in the database 203 associated with thegiven podcast audio file.

Yet another aspect is directed to a non-transitory computer-readablemedium for operating an audio podcast distribution system 200 comprisingat least one computing device 204 a-204 n, and a server 201 configuredto aggregate and store a plurality of podcast audio files 202 in adatabase 203. The non-transitory computer-readable medium hascomputer-executable instructions for causing the at least one computingdevice 204 a-204 n and the server 201 to perform steps of the abovedescribed method.

Referring now additionally to FIG. 23 , another embodiment of the audiopodcast distribution system 300 is now described. In this embodiment ofthe audio podcast distribution system 300, those elements alreadydiscussed above with respect to FIGS. 1-16 are incremented by 200 andmost require no further discussion herein. This embodiment differs fromthe previous embodiment in that this processor 306 is configured to whenthe audio snippet creation user input 312 is activated, render an audiosnippet creation GUI 313 (FIGS. 12-15 ) for generating an audio snippet314 of the given podcast audio file 302, and upload plurality of fileparameters for the audio snippet of the given podcast audio file to thedatabase 303. The plurality of file parameters may comprise an episodeID, a user ID, a start time, and a time duration, for example. As willbe appreciated, the plurality of file parameters is used by the serverto 301 to create the audio snippet 314. In other embodiments, the audiosnippet 314 may be created on the computing device 304 a.

Many modifications and other embodiments of the present disclosure willcome to the mind of one skilled in the art having the benefit of theteachings presented in the foregoing descriptions and the associateddrawings. Therefore, it is understood that the present disclosure is notto be limited to the specific embodiments disclosed, and thatmodifications and embodiments are intended to be included within thescope of the appended claims.

The invention claimed is:
 1. An audio podcast distribution systemcomprising: a server configured to aggregate and store a plurality ofpodcast audio files in a database; and at least one computing device incommunication with the server, the at least one computing devicecomprising a processor and a display coupled to the processor, theprocessor configured to render an audio playback graphical userinterface (GUI) on the display for playing a given podcast audio filefrom the database, the audio playback GUI comprising a playback controluser input, and an audio snippet creation user input, when the audiosnippet creation user input is activated, render an audio snippetcreation GUI for generating an audio snippet of the given podcast audiofile, and upload at least one file parameter for the audio snippet ofthe given podcast audio file to the database, render an audio snippetplayback GUI on the display, the audio snippet playback GUI comprising avideo creation user input, and when the video creation user input isactivated, send a video request to the server, the video request beingassociated with the audio snippet of the given podcast audio file; theserver configured to, based upon the video request, generate a videofile comprising the audio snippet of the given podcast audio file, andimage data in the database associated with the given podcast audio file.2. The audio podcast distribution system of claim 1 wherein the serveris configured to add the video file of the audio snippet of the givenpodcast audio file to the database, and generate a custom link to accessthe video file within the database.
 3. The audio podcast distributionsystem of claim 1 wherein the server is configured to generate the videofile by at least generating sequential screenshots of the audio snippetplayback GUI, and combining the sequential screenshots with the audiosnippet of the given podcast audio file.
 4. The audio podcastdistribution system of claim 1 wherein the server is configured toaccess the video file when another video request is received for thesame audio snippet of the given podcast audio file.
 5. The audio podcastdistribution system of claim 1 wherein the audio snippet creation GUIcomprises a visual waveform input, and an audio snippet creationplayback control user input.
 6. The audio podcast distribution system ofclaim 1 wherein the server is configured to add the audio snippet of thegiven podcast audio file to the database, and generate a custom link toaccess the audio snippet within the database.
 7. The audio podcastdistribution system of claim 1 wherein the at least one computing devicecomprises a plurality of computing devices configured to respectivelyupload a plurality of audio snippets to the server; and wherein theserver is configured to rank the plurality of audio snippets based uponheuristics data for respective users associated with the plurality ofcomputing devices.
 8. The audio podcast distribution system of claim 7wherein the heuristic data comprises audio playback data and audioplayback completion event data.
 9. The audio podcast distribution systemof claim 7 wherein the processor is configured to render an audiosnippet discovery GUI on the display for viewing the plurality of audiosnippets, the audio snippet discovery GUI configured to receive swipeinput to scroll through the plurality of audio snippets.
 10. A methodfor operating an audio podcast distribution system comprising at leastone computing device, and a server configured to aggregate and store aplurality of podcast audio files in a database, the at least onecomputing device in communication with the server, the methodcomprising: rendering an audio playback graphical user interface (GUI)on a display of the at least one computing device for playing a givenpodcast audio file from the database, the audio playback GUI comprisinga playback control user input, and an audio snippet creation user input;when the audio snippet creation user input is activated, rendering anaudio snippet creation GUI on the display of the at least one computingdevice for generating an audio snippet of the given podcast audio file,and uploading at least one file parameter for the audio snippet of thegiven podcast audio file to the database; rendering an audio snippetplayback GUI on the display of the at least one computing device, theaudio snippet playback GUI comprising a video creation user input; whenthe video creation user input is activated, send a video request to theserver, the video request being associated with the audio snippet of thegiven podcast audio file; and generating, at the server, based upon thevideo request a video file comprising the audio snippet of the givenpodcast audio file, and image data in the database associated with thegiven podcast audio file.
 11. The method of claim 10 further comprising,at the server, adding the video file of the audio snippet of the givenpodcast audio file to the database, and generating a custom link toaccess the video file within the database.
 12. The method of claim 10further comprising, at the server, generating the video file by at leastgenerating sequential screenshots of the audio snippet playback GUI, andcombining the sequential screenshots with the audio snippet of the givenpodcast audio file.
 13. The method of claim 10 further comprising, atthe server, accessing the video file when another video request isreceived for the same audio snippet of the given podcast audio file. 14.The method of claim 10 wherein the audio snippet creation GUI comprisesa visual waveform input, and an audio snippet creation playback controluser input.
 15. The method of claim 10 wherein the at least onecomputing device comprises a plurality of computing devices configuredto respectively upload a plurality of audio snippets to the server; andwherein the server is configured to rank the plurality of audio snippetsbased upon heuristics data for respective users associated with theplurality of computing devices.
 16. The method of claim 15 wherein theheuristic data comprises audio playback data and audio playbackcompletion event data; and further comprising rendering an audio snippetdiscovery GUI on the display for viewing the plurality of audiosnippets, the audio snippet discovery GUI configured to receive swipeinput to scroll through the plurality of audio snippets.
 17. Anon-transitory computer-readable medium for operating an audio podcastdistribution system comprising at least one computing device, and aserver configured to aggregate and store a plurality of podcast audiofiles in a database, the at least one computing device in communicationwith the server, the non-transitory computer-readable medium havingcomputer-executable instructions for causing the at least one computingdevice and the server to perform steps comprising: rendering an audioplayback graphical user interface (GUI) on a display of the at least onecomputing device for playing a given podcast audio file from thedatabase, the audio playback GUI comprising a playback control userinput, and an audio snippet creation user input; when the audio snippetcreation user input is activated, rendering an audio snippet creationGUI on the display of the at least one computing device for generatingan audio snippet of the given podcast audio file, and uploading at leastone file parameter for the audio snippet of the given podcast audio fileto the database; rendering an audio snippet playback GUI on the displayof the at least one computing device, the audio snippet playback GUIcomprising a video creation user input; when the video creation userinput is activated, send a video request to the server, the videorequest being associated with the audio snippet of the given podcastaudio file; and generating, at the server, based upon the video requesta video file comprising the audio snippet of the given podcast audiofile, and image data in the database associated with the given podcastaudio file.
 18. The non-transitory computer-readable medium of claim 17wherein the steps includes, at the server, adding the video file of theaudio snippet of the given podcast audio file to the database, andgenerating a custom link to access the video file within the database.19. The non-transitory computer-readable medium of claim 17 wherein thesteps includes, at the server, generating the video file by at leastgenerating sequential screenshots of the audio snippet playback GUI, andcombining the sequential screenshots with the audio snippet of the givenpodcast audio file.
 20. The non-transitory computer-readable medium ofclaim 17 wherein the steps includes, at the server, accessing the videofile when another video request is received for the same audio snippetof the given podcast audio file.